Remove normative text from IANA considerations#1075
Remove normative text from IANA considerations#1075robUx4 merged 2 commits intoietf-wg-cellar:masterfrom
Conversation
cellar-tags/tags_iana.md
Outdated
| A Tag Name **MUST** only be found once in the IANA registry. | ||
| Two Tag Names **MUST NOT** have the same semantic meaning. | ||
| The Name is written in all latin capital letters, numbers and the underscore character '_' | ||
| as defined in (#tag-formatting). The Name **MUST NOT** start with the underscore character '_'. |
There was a problem hiding this comment.
I suggest that you move "The Name MUST NOT start with the underscore character '_'." to tag-formatting section.
There was a problem hiding this comment.
This would also help with Mike Bishops comments
There was a problem hiding this comment.
@robUx4 - I agree with @boucadair and @OR13 here. Please make the proposed change.
There was a problem hiding this comment.
There's one left with the underscore but it's already part of the rules defined in 3.2.1.
So just not repeat it here ? We assume the people at IANA that will approve the "First Come First Serve" names will also check that paragraph ?
There was a problem hiding this comment.
The format needs to follow the rules you have in tag-formatting section. If you want to emphasis on that specific part, you may consider making this change here under IANA section:
OLD:
The Name MUST NOT start with the underscore character '_'
NEW:
As specified in (#tag-formatting), the Name must not start with the underscore character '_'.
There was a problem hiding this comment.
That was going to be my next question: can it be the same text but non normative.
I applied the change as suggested :)
There was a problem hiding this comment.
:-)
I think that we can close this one.
Thank you
The rule of First Come First Served involves that the name can't be found twice and (hopefully) the same thing can't be defined in 2 different ways.
d13f2b0 to
e86a5dd
Compare
There's one left with the underscore but it's already part of the rules defined in 3.2.1.
cc @boucadair @SpencerDawkins